#log4j2 maven | Explore Tumblr posts and blogs

nicola-top · 3 years ago

Text

Как скачать и установить Debian 10 Buster

Установка Debian 10 Buster или 11, 9 или 8, не столь важно. Важно то, что создание сервера, начинается именно с инсталляции ОС. Установка Debian может проводиться на ПК, ноутбук или на полноценное серверное оборудование. Важно понимать, что Linux системы предназначены для администрирования серверов. Поэтому установка дистрибутива Debian, является первостепенной задачей. В прошлых руководствах я рассказывал про установку debian 8.5 jessie и debian 9.1 stretch, шаги по установке не изменились. Нам по прежнему необходимо выполнить все те же действия.

Debian по прежнему является ключевым дистрибутивом Linux. Система стара и востребована, считается, что дистрибутив Debian наиболее безопасен и защищен в отличии от других Linux-систем. Тем не менее поддержка этого дистрибутива разработчиками закончится уже через пару лет.

Повышенная стабильность — самый важный фактор, который мне нравиться в Debian.

Выпуск нового обновленного релиза вышел 26 марта 2022 года Debian 10 buster. Дистрибутив имеет множество исправлений безопасности системы. Более строгие алгоритмы проверки подписей OpenSSL.

Исправлено большое количество существующих ошибок в пакетах и компонентах, вот небольшая выписка: apache-log4j1.2, apache-log4j2, atftp, base-files, beads, btrbk, cargo-mozilla, chrony, cimg, clamav, cups, debian-installer, debian-installer-netboot-images, detox, evolution-data-server, inux-signed-amd64, linux-signed-arm64, linux-signed-i386, llvm-toolchain-11 и т.д.

Обновлены пакеты безопасности системы, вот некоторые из них: samba, apache2, neutron, wordpress, tomcat9, squashfs-tools, php7.3, bind9, postgresql-11, libxml-security-java, apache-log4j2, xorg-server, spip, djvulibre, debian-edu-config, h2database, linux-signed-amd64, linux-signed-arm64, linux-signed-i386, tryton-server и т.д

Удалены бесполезные пакеты: angular-maven-plugin и minify-maven-plugin. В этом руководстве я расскажу как установить Debian 10 buster на компьютер, ноутбук или серверное оборудование. Для последующей настройки и установки программного обеспечения для сервера.

Источник тут: https://nicola.top/kak-skachat-i-ustanovit-debian-10-buster/

0 notes

trebarobota · 6 years ago

Photo

Senior JavaFX Developer Cosylab Ukraine Requirements: Strong Java 8 programming skills; RHEL/Centos, Java 8, Scala 2, maven, bash, Zero MQ, Immutables, log4j2, jackson, mockito, sonar, eclipse…

#Київ

0 notes

zz04-com · 5 years ago

Text

Plumelog分布式日志组件 v3.1

Plumelog一个简单易用的java分布式日志组件。支持百亿级别，日志从搜集到查询，不用去文件中翻阅日志方便快捷，支持查询一个调用链的日志，支持链路追踪，查看调用链耗时情况，在分布式系统中也可以查询关联日志，能够帮助快速定位问题，简单易用，没有代码入侵，查询界面友好，高效，方便，只要你是java系统，不要做任何项目改造，接入直接使用，日志不落本地磁盘，无需关心日志占用应用服务器磁盘问题,觉得项目好用帮忙点个星星，您的star是我们前进的动力。

Plumelog功能介绍：

1、无入侵的分布式日志系统，基于log4j、log4j2、logback搜集日志，设置链路ID，方便查询关联日志

2、基于elasticsearch作为查询引擎

3、高吞吐，查询效率高

4、全程不占应用程序本地磁盘空间，免维护;对于项目透明，不影响项目本身运行

5、无需修改老项目，引入直接使用，支持dubbo,支持springcloud

Plumelog架构：

plumelog-core：核心组件包含日志搜集端，负责搜集日志并推送到kafka，redis等队列

plumelog-server：负责把队列中的日志日志异步写入到elasticsearch

plumelog-ui：前端展示，日志查询界面

plumelog-demo：基于springboot的使用案例

Plumelog使用方法：

自己编译安装如下

前提:kafka或者redis 和 elasticsearch（版本6.8以上最好）自行安装完毕，版本兼容已经做了，理论不用考虑ES版本

打包

maven deploy -DskipTests 上传包到自己的私服

私服地址到plumelog/pom.xml改

UTF-8

http://172.16.249.94:4000

from 站长源码 https://zz04.net/6485.html

#站长源码

0 notes

faizrashis1995 · 6 years ago

Text

How to run AWS CloudHSM workloads on Docker containers

AWS CloudHSM is a cloud-based hardware security module (HSM) that enables you to generate and use your own encryption keys on the AWS Cloud. With CloudHSM, you can manage your own encryption keys using FIPS 140-2 Level 3 validated HSMs. Your HSMs are part of a CloudHSM cluster. CloudHSM automatically manages synchronization, high availability, and failover within a cluster.

CloudHSM is part of the AWS Cryptography suite of services, which also includes AWS Key Management Service (KMS) and AWS Certificate Manager Private Certificate Authority (ACM PCA). KMS and ACM PCA are fully managed services that are easy to use and integrate. You’ll generally use AWS CloudHSM only if your workload needs a single-tenant HSM under your own control, or if you need cryptographic algorithms that aren’t available in the fully-managed alternatives.

CloudHSM offers several options for you to connect your application to your HSMs, including PKCS#11, Java Cryptography Extensions (JCE), or Microsoft CryptoNG (CNG). Regardless of which library you choose, you’ll use the CloudHSM client to connect to all HSMs in your cluster. The CloudHSM client runs as a daemon, locally on the same Amazon Elastic Compute Cloud (EC2) instance or server as your applications.

The deployment process is straightforward if you’re running your application directly on your compute resource. However, if you want to deploy applications using the HSMs in containers, you’ll need to make some adjustments to the installation and execution of your application and the CloudHSM components it depends on. Docker containers don’t typically include access to an init process like systemd or upstart. This means that you can’t start the CloudHSM client service from within the container using the general instructions provided by CloudHSM. You also can’t run the CloudHSM client service remotely and connect to it from the containers, as the client daemon listens to your application using a local Unix Domain Socket. You cannot connect to this socket remotely from outside the EC2 instance network namespace.

This blog post discusses the workaround that you’ll need in order to configure your container and start the client daemon so that you can utilize CloudHSM-based applications with containers. Specifically, in this post, I’ll show you how to run the CloudHSM client daemon from within a Docker container without needing to start the service. This enables you to use Docker to develop, deploy and run applications using the CloudHSM software libraries, and it also gives you the ability to manage and orchestrate workloads using tools and services like Amazon Elastic Container Service (Amazon ECS), Kubernetes, Amazon Elastic Container Service for Kubernetes (Amazon EKS), and Jenkins.

Solution overview

My solution shows you how to create a proof-of-concept sample Docker container that is configured to run the CloudHSM client daemon. When the daemon is up and running, it runs the AESGCMEncryptDecryptRunner Java class, available on the AWS CloudHSM Java JCE samples repo. This class uses CloudHSM to generate an AES key, then it uses the key to encrypt and decrypt randomly generated data.

Note: In my example, you must manually enter the crypto user (CU) credentials as environment variables when running the container. For any production workload, you’ll need to carefully consider how to provide, secure, and automate the handling and distribution of your HSM credentials. You should work with your security or compliance officer to ensure that you’re using an appropriate method of securing HSM login credentials for your application and security needs.

Figure 1: Architectural diagram

Prerequisites

To implement my solution, I recommend that you have basic knowledge of the below:

CloudHSM

Docker

Java

Here’s what you’ll need to follow along with my example:

An active CloudHSM cluster with at least one active HSM. You can follow the Getting Started Guide to create and initialize a CloudHSM cluster. (Note that for any production cluster, you should have at least two active HSMs spread across Availability Zones.)

An Amazon Linux 2 EC2 instance in the same Amazon Virtual Private Cloud in which you created your CloudHSM cluster. The EC2 instance must have the CloudHSM cluster security group attached—this security group is automatically created during the cluster initialization and is used to control access to the HSMs. You can learn about attaching security groups to allow EC2 instances to connect to your HSMs in our online documentation.

A CloudHSM crypto user (CU) account created on your HSM. You can create a CU by following these user guide steps.

Solution details

On your Amazon Linux EC2 instance, install Docker:

# sudo yum -y install docker

Start the docker service:

# sudo service docker start

Create a new directory and step into it. In my example, I use a directory named “cloudhsm_container.” You’ll use the new directory to configure the Docker image.

# mkdir cloudhsm_container

# cd cloudhsm_container

Copy the CloudHSM cluster’s CA certificate (customerCA.crt) to the directory you just created. You can find the CA certificate on any working CloudHSM client instance under the path /opt/cloudhsm/etc/customerCA.crt. This certificate is created during initialization of the CloudHSM Cluster and is needed to connect to the CloudHSM cluster.

In your new directory, create a new file with the name run_sample.sh that includes the contents below. The script starts the CloudHSM client daemon, waits until the daemon process is running and ready, and then runs the Java class that is used to generate an AES key to encrypt and decrypt your data.

#! /bin/bash

# start cloudhsm client

echo -n "* Starting CloudHSM client ... "

/opt/cloudhsm/bin/cloudhsm_client /opt/cloudhsm/etc/cloudhsm_client.cfg &> /tmp/cloudhsm_client_start.log &

# wait for startup

while true

if grep 'libevmulti_init: Ready !' /tmp/cloudhsm_client_start.log &> /dev/null

then

echo "[OK]"

break

sleep 0.5

done

echo -e "\n* CloudHSM client started successfully ... \n"

# start application

echo -e "\n* Running application ... \n"

java -ea -Djava.library.path=/opt/cloudhsm/lib/ -jar target/assembly/aesgcm-runner.jar --method environment

echo -e "\n* Application completed successfully ... \n"

In the new directory, create another new file and name it Dockerfile (with no extension). This file will specify that the Docker image is built with the following components:

The AWS CloudHSM client package.

The AWS CloudHSM Java JCE package.

OpenJDK 1.8. This is needed to compile and run the Java classes and JAR files.

Maven, a build automation tool that is needed to assist with building the Java classes and JAR files.

The AWS CloudHSM Java JCE samples that will be downloaded and built.

Cut and paste the contents below into Dockerfile.

Note: Make sure to replace the HSM_IP line with the IP of an HSM in your CloudHSM cluster. You can get your HSM IPs from the CloudHSM console, or by running the describe-clusters AWS CLI command.

# Use the amazon linux image

FROM amazonlinux:2

# Install CloudHSM client

RUN yum install -y https://s3.amazonaws.com/cloudhsmv2-software/CloudHsmClient/EL7/cloudhsm-client-latest.el7.x86_64.rpm

# Install CloudHSM Java library

RUN yum install -y https://s3.amazonaws.com/cloudhsmv2-software/CloudHsmClient/EL7/cloudhsm-client-jce-latest.el7.x86_64.rpm

# Install Java, Maven, wget, unzip and ncurses-compat-libs

RUN yum install -y java maven wget unzip ncurses-compat-libs

# Create a work dir

WORKDIR /app

# Download sample code

RUN wget https://github.com/aws-samples/aws-cloudhsm-jce-examples/archive/master.zip

# unzip sample code

RUN unzip master.zip

# Change to the create directory

WORKDIR aws-cloudhsm-jce-examples-master

# Build JAR files

RUN mvn validate && mvn clean package

# Set HSM IP as an environmental variable

ENV HSM_IP <insert the IP address of an active CloudHSM instance here>

# Configure cloudhms-client

COPY customerCA.crt /opt/cloudhsm/etc/

RUN /opt/cloudhsm/bin/configure -a $HSM_IP

# Copy the run_sample.sh script

COPY run_sample.sh .

# Run the script

CMD ["bash","run_sample.sh"]

Now you’re ready to build the Docker image. Use the following command, with the name jce_sample_client. This command will let you use the Dockerfile you created in step 6 to create the image.

# sudo docker build -t jce_sample_client .

To run a Docker container from the Docker image you just created, use the following command. Make sure to replace the user and password with your actual CU username and password. (If you need help setting up your CU credentials, see prerequisite 3. For more information on how to provide CU credentials to the AWS CloudHSM Java JCE Library, refer to the steps in the CloudHSM user guide.)

# sudo docker run --env HSM_PARTITION=PARTITION_1 \

--env HSM_USER=<user> \

--env HSM_PASSWORD=<password> \

jce_sample_client

If successful, the output should look like this:

* Starting cloudhsm-client ... [OK]

* cloudhsm-client started successfully ...

* Running application ...

ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors

to the console.

70132FAC146BFA41697E164500000000

Successful decryption

SDK Version: 2.03

* Application completed successfully ...

Conclusion

My solution provides an example of how to run CloudHSM workloads on Docker containers. You can use it as a reference to implement your cryptographic application in a way that benefits from the high availability and load balancing built in to AWS CloudHSM without compromising on the flexibility that Docker provides for developing, deploying, and running applications. If you have comments about this post, submit them in the Comments section below.[Source]-https://aws.amazon.com/blogs/security/how-to-run-aws-cloudhsm-workloads-on-docker-containers/

Beginners & Advanced level Docker Training Course in Mumbai. Asterix Solution's 25 Hour Docker Training gives broad hands-on practicals. For details, Visit :

0 notes

terabitweb · 6 years ago

Text

Original Post from Amazon Security Author: Mohamed AboElKheir

Solution overview

Figure 1: Architectural diagram

Prerequisites

To implement my solution, I recommend that you have basic knowledge of the below:

CloudHSM

Docker

Java

Here’s what you’ll need to follow along with my example:

A CloudHSM crypto user (CU) account created on your HSM. You can create a CU by following these user guide steps.

Solution details

On your Amazon Linux EC2 instance, install Docker:

# sudo yum -y install docker

Start the docker service:

# sudo service docker start

Create a new directory and step into it. In my example, I use a directory named “cloudhsm_container.” You’ll use the new directory to configure the Docker image.

# mkdir cloudhsm_container # cd cloudhsm_container

#! /bin/bash # start cloudhsm client echo -n "* Starting CloudHSM client ... " /opt/cloudhsm/bin/cloudhsm_client /opt/cloudhsm/etc/cloudhsm_client.cfg &> /tmp/cloudhsm_client_start.log & # wait for startup while true do if grep 'libevmulti_init: Ready !' /tmp/cloudhsm_client_start.log &> /dev/null then echo "[OK]" break fi sleep 0.5 done echo -e "n* CloudHSM client started successfully ... n" # start application echo -e "n* Running application ... n" java -ea -Djava.library.path=/opt/cloudhsm/lib/ -jar target/assembly/aesgcm-runner.jar --method environment echo -e "n* Application completed successfully ... n"

In the new directory, create another new file and name it Dockerfile (with no extension). This file will specify that the Docker image is built with the following components:

The AWS CloudHSM client package.

The AWS CloudHSM Java JCE package.

OpenJDK 1.8. This is needed to compile and run the Java classes and JAR files.

Maven, a build automation tool that is needed to assist with building the Java classes and JAR files.

The AWS CloudHSM Java JCE samples that will be downloaded and built.

Cut and paste the contents below into Dockerfile.

Note: Make sure to replace the HSM_IP line with the IP of an HSM in your CloudHSM cluster. You can get your HSM IPs from the CloudHSM console, or by running the describe-clusters AWS CLI command.

# Use the amazon linux image FROM amazonlinux:2 # Install CloudHSM client RUN yum install -y https://s3.amazonaws.com/cloudhsmv2-software/CloudHsmClient/EL7/cloudhsm-client-latest.el7.x86_64.rpm # Install CloudHSM Java library RUN yum install -y https://s3.amazonaws.com/cloudhsmv2-software/CloudHsmClient/EL7/cloudhsm-client-jce-latest.el7.x86_64.rpm # Install Java, Maven, wget, unzip and ncurses-compat-libs RUN yum install -y java maven wget unzip ncurses-compat-libs # Create a work dir WORKDIR /app # Download sample code RUN wget https://github.com/aws-samples/aws-cloudhsm-jce-examples/archive/master.zip # unzip sample code RUN unzip master.zip # Change to the create directory WORKDIR aws-cloudhsm-jce-examples-master # Build JAR files RUN mvn validate && mvn clean package # Set HSM IP as an environmental variable ENV HSM_IP <insert the IP address of an active CloudHSM instance here> # Configure cloudhms-client COPY customerCA.crt /opt/cloudhsm/etc/ RUN /opt/cloudhsm/bin/configure -a $HSM_IP # Copy the run_sample.sh script COPY run_sample.sh . # Run the script CMD ["bash","run_sample.sh"]

Now you’re ready to build the Docker image. Use the following command, with the name jce_sample_client. This command will let you use the Dockerfile you created in step 6 to create the image.

# sudo docker build -t jce_sample_client .

# sudo docker run --env HSM_PARTITION=PARTITION_1 --env HSM_USER=<user> --env HSM_PASSWORD=<password> jce_sample_client

If successful, the output should look like this:

* Starting cloudhsm-client ... [OK] * cloudhsm-client started successfully ... * Running application ... ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. 70132FAC146BFA41697E164500000000 Successful decryption SDK Version: 2.03 * Application completed successfully ...

Conclusion

Want more AWS Security how-to content, news, and feature announcements? Follow us on Twitter.

Mohamed AboElKheir

Mohamed AboElKheir joined AWS in September 2017 as a Security CSE (Cloud Support Engineer) based in Cape Town. He is a subject matter expert for CloudHSM and is always enthusiastic about assisting CloudHSM customers with advanced issues and use cases. Mohamed is passionate about InfoSec, specifically cryptography, penetration testing (he’s OSCP certified), application security, and cloud security (he’s AWS Security Specialty certified).

#gallery-0-5 { margin: auto; } #gallery-0-5 .gallery-item { float: left; margin-top: 10px; text-align: center; width: 33%; } #gallery-0-5 img { border: 2px solid #cfcfcf; } #gallery-0-5 .gallery-caption { margin-left: 0; } /* see gallery_shortcode() in wp-includes/media.php */

Go to Source Author: Mohamed AboElKheir How to run AWS CloudHSM workloads on Docker containers Original Post from Amazon Security Author: Mohamed AboElKheir AWS CloudHSM is a cloud-based hardware security module (HSM) that enables you to generate and use your own encryption keys on the AWS Cloud.

#Amazon Security

0 notes

lewiskdavid90 · 8 years ago

Text

88% off #SDLC with SOA Spring Java JMS GIT ActiveMQ MongoDB Jenkins – $10

Learn to Plan Define Design Code Test & Deploy w/ SOA Spring ActiveMQ Git Jenkins Cobertura JSON Java Messaging MongoDB

All Levels, – 7 hours, 84 lectures

Average rating 4.0/5 (4.0 (113 ratings) Instead of using a simple lifetime average, Udemy calculates a course’s star rating by considering a number of different factors such as the number of ratings, the age of ratings, and the likelihood of fraudulent ratings.)

Course requirements:

Have some Java programming experience

Course description:

You will learn the complete software development life cycle creating a Spring JMS Service Oriented Application using tools like:

Eclipse Spring Framework JMS JUnit Log4j2 ActiveMQ GIT Jenkins Continuous Integration Cobetura Code Coverage Git with BitBucket Tomcat 7 and 8.

By the end of the course you will have complete understanding of the software development lifecycle and have complete confidence using the tools in this course to create service oriented architecture applications in any workplace.

Full details Complete a Spring JMS Application using the complete SDLC Become familiar and confident with the Service Oriented Architecture Have complete confidence with the tools used in this course Beginner and Novice Programmers, Developers, Designers, Architects

Reviews:

“THIS HAS BECOME THE MOST CHALLENGING WONDERFUL EXPERIENCE AND THANK YOU SO MUCH FOR TEACHING IT. I have gone through lots of ups and downs and got everything to work beautifully.” (Chris Vetek)

“I couldn’t progress with the course because I had some issues with the spring templates. Here you can read my issues https://www.udemy.com/sdlc-with-soa-spring-jms-git-activemq-mongodb-jenkins/learn/v4/questions/1685360 The teacher couldn’t give me any advice about how to progress without that, then, I gave up. I watched the videos, in the future, when I have more experience I will try to go back. For me, it was not useful.” (Carmen Gamez)

“Thank you. Maybe a little bit more theory would be better. The full project is working properly on my side with all the technologies.” (Kovács Róbert)

About Instructor:

Eric Clarke

With 20 years of business and information technology, teaching, and consulting experience as a project manager, project lead, software developer, designer, architect, adjunct professor, and trainer with extensive experience in software development, innovation, and design. Development with tools like J2EE, Java, IBM Broker, WSRR, Service Mix, Apache Camel, ActiveMQ, PHP, AJAX, XML, MongoDB, MySQL, DB2, Oracle, Git, Subversion, CVS, Struts, EJBs, Web Services, Ant, Maven, JUnit, JMeter, Jenkins, Cobertura, Excel, Word, Powerpoint, and many other web technologies.

Instructor Other Courses:

…………………………………………………………… Eric Clarke coupons Development course coupon Udemy Development course coupon Programming Languages course coupon Udemy Programming Languages course coupon SDLC with SOA Spring Java JMS GIT ActiveMQ MongoDB Jenkins SDLC with SOA Spring Java JMS GIT ActiveMQ MongoDB Jenkins course coupon SDLC with SOA Spring Java JMS GIT ActiveMQ MongoDB Jenkins coupon coupons

The post 88% off #SDLC with SOA Spring Java JMS GIT ActiveMQ MongoDB Jenkins – $10 appeared first on Course Tag.

from Course Tag http://coursetag.com/udemy/coupon/88-off-sdlc-with-soa-spring-java-jms-git-activemq-mongodb-jenkins-10/ from Course Tag https://coursetagcom.tumblr.com/post/158276020228

0 notes